Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0140

reference: 181-tree-1
name: 0140
tree-preservation-order: undefined
181-tpo-1
uprn
address-text
point: POINT (-0.939727 50.865475)
geometry: MULTIPOLYGON (((-0.939656 50.865467,-0.939659 50.865481,-0.939669 50.865494,-0.939685 50.865504,-0.939704 50.865510,-0.939726 50.865513,-0.939748 50.865511,-0.939768 50.865505,-0.939784 50.865495,-0.939794 50.865482,-0.939798 50.865468,-0.939795 50.865455,-0.939785 50.865442,-0.939770 50.865432,-0.939750 50.865425,-0.939728 50.865423,-0.939706 50.865425,-0.939686 50.865431,-0.939670 50.865441,-0.939660 50.865453,-0.939656 50.865467)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL